Steps:

```shell
$ npm install
$ npm update
```

Part of #61

Run `npm run pre-checkin` after dependency changes in previous commits.

Fixes #61

Follows up #61

Part of #60

GitHub doesn't support Ubuntu Focal runners anymore.

actions/runner-images#11101

It is EOL and the jobs are failing with the following errors:

> E: The repository 'http://deb.debian.org/debian buster Release' does
>    not have a Release file.

> E: The repository 'http://deb.debian.org/debian-security
>    buster/updates Release' does not have a Release file.

> E: The repository 'http://deb.debian.org/debian buster-updates
>    Release' does not have a Release file.

Part of #62

There are a few places, where we assume that only amd64 exists. Let's
take the architecture into account.

It solves two problems:

* Now we fetch appropriate tarantool versions list (#60).
* Now the architecture is a part of the cache key (#62).

Fixes #60
Fixes #62

We have no packages built against Ubuntu Jammy (22.04) for tarantool
2.4-2.9, while the previous Ubuntu version is not supported anymore by
GitHub hosted runners. It is problematic to test installation of these
versions in CI.

In fact, these versions are not supported for a long time, so let's just
drop them from the testing.

We have no 1.10 builds for Ubuntu Noble. Particular tarantool version is
not important for this testing scenario, so use 2.11 instead.

We have no 1.10 builds for Ubuntu Noble (24.04). Let's use Ubuntu Jammy
for these tests.

We have no 2.10 builds for Ubuntu Noble (24.04). Let's use 2.11 instead.

NB: 2.11 builds exists for Ubuntu Noble since 2.11.6.